Sourced from flex_color_scheme's releases.

Version 8.2.0

8.2.0

March 23, 2025

Package

CHORE

• Update the package to support and require at least Flutter v3.29.0.
  • Remove all usage and references to new deprecated properties in Flutter 3.29.0:
    • MaterialStateUnderlineInputBorder → WidgetStateInputBorder
    • MaterialStateOutlineInputBorder → WidgetStateInputBorder
    • Themedata.dialogBackgroundColor: Removed all usage and references in the FCS packages and Themes Playground app.
• Remove all usage and references to new deprecated properties in Flutter 3.31.0 BETA:
  • ThemeData.indicatorColor: Removed all usage and references in the FCS packages and Themes Playground app. FlexColorScheme has not used this property for a while, but kept it defined while it still existed. It is deprecated in Flutter 3.31.0 BETA and will be so in next stable Flutter release as well. FCS 8.2.0 stops defining any value for it and also removes it from the Themes Playground app. It has in FCS for a long time already been replaced by TabBarThemeData.indicatorColor. Test were now also updated to use this reference instead of the to be deprecated one.
• Fix lints for the stable, beta and master channels.
• FlexColorScheme is still using pre-Dart 3.7.0 formatter. It will change to new format, with longer line length, when the Flutter stable channel supports manual trailing comma. Change to the new formatter was tested, but reverted because it was horrible.

FIX

• Fix TabBarTheme normalization Flutter SDK breaking change on the master and beta channel, see [issue #276](rydmike/flex_color_scheme#276).
  • The TabBar theme API had breaking changes in Flutter 3.27 release. These were addressed in FlexColorScheme v8.1.0. In Flutter 3.31 (beta) there are additional compile-time breaking changes not present in Flutter 3.29 and earlier versions. FlexColorScheme v8.2.0 is compatible with these Flutter SDK breaking changes. For more information, see the TabBar theme API breaking changes, that documented the in Flutter 3.27 breaking changes. Apparently, something more changed now, as the TabBar theming that still works in Flutter 3.29, broke again in Flutter 3.31 beta and later. Regardless of what and why it was broken, FCS v8.2.0 fixes the usage of the compile-time broken API, it now works again, with at release time used APIs in Flutter stable, beta and master channels.

NEW

• Beta feature:

  • Added Shadcn UI color schemes. This includes, custom classes to store the Shadcn color tokens, FlexSchemeColor implementations of them and FlexScheme enums of the configs to make it easy to use them.

    The FlexScheme enums for using the Shadcn colors are:

    • FlexScheme.shadBlue
    • FlexScheme.shadGray
    • FlexScheme.shadGreen
    • FlexScheme.shadNeutral
    • FlexScheme.shadOrange
    • FlexScheme.shadRed
    • FlexScheme.shadRose
    • FlexScheme.shadSlate
    • FlexScheme.shadStone
    • FlexScheme.shadViolet
    • FlexScheme.shadYellow
    • FlexScheme.shadZinc

  • The Shadcn color schemes are still considered beta. The current version does not yet support or use the Shadcn default colors for background, surface and container colors. In this release those colors are using FlexColorScheme's monochrome surface colors. Later versions may change this and use the Shadcn surface colors by default when selecting these themes, with an option to switch to FlexColorScheme's monochrome surface colors, which this version currently uses as the only choice.

  • The Shadcn color selections only set default colors, you will have to theme Material to look more like Shadcn yourself by selecting the correct Material components and modifying their properties to look and behave more like Shadcn style. The Themes Playground includes a pre-configured very preliminary configuration that you can use to do this.

  • The Shadcn color features are in this beta release excluded from FlexColorScheme's otherwise rigorous tests.

Themes Playground

FIX

• Playground: Fix code gen for the first scheme, see [issue #275](rydmike/flex_color_scheme#275).

... (truncated)

Sourced from flex_color_scheme's changelog.

8.2.0

March 23, 2025

Package

CHORE

• Update the package to support and require at least Flutter v3.29.0.
  • Remove all usage and references to new deprecated properties in Flutter 3.29.0:
    • MaterialStateUnderlineInputBorder → WidgetStateInputBorder
    • MaterialStateOutlineInputBorder → WidgetStateInputBorder
    • Themedata.dialogBackgroundColor: Removed all usage and references in the FCS packages and Themes Playground app.
• Remove all usage and references to new deprecated properties in Flutter 3.31.0 BETA:
  • ThemeData.indicatorColor: Removed all usage and references in the FCS packages and Themes Playground app. FlexColorScheme has not used this property for a while, but kept it defined while it still existed. It is deprecated in Flutter 3.31.0 BETA and will be so in next stable Flutter release as well. FCS 8.2.0 stops defining any value for it and also removes it from the Themes Playground app. It has in FCS for a long time already been replaced by TabBarThemeData.indicatorColor. Test were now also updated to use this reference instead of the to be deprecated one.
• Fix lints for the stable, beta and master channels.
• FlexColorScheme is still using pre-Dart 3.7.0 formatter. It will change to new format, with longer line length, when the Flutter stable channel supports manual trailing comma. Change to the new formatter was tested, but reverted because it was horrible.

FIX

• Fix TabBarTheme normalization Flutter SDK breaking change on the master and beta channel, see [issue #276](rydmike/flex_color_scheme#276).
  • The TabBar theme API had breaking changes in Flutter 3.27 release. These were addressed in FlexColorScheme v8.1.0. In Flutter 3.31 (beta) there are additional compile-time breaking changes not present in Flutter 3.29 and earlier versions. FlexColorScheme v8.2.0 is compatible with these Flutter SDK breaking changes. For more information, see the TabBar theme API breaking changes, that documented the in Flutter 3.27 breaking changes. Apparently, something more changed now, as the TabBar theming that still works in Flutter 3.29, broke again in Flutter 3.31 beta and later. Regardless of what and why it was broken, FCS v8.2.0 fixes the usage of the compile-time broken API, it now works again, with at release time used APIs in Flutter stable, beta and master channels.

NEW

• Beta feature:

  • Added Shadcn UI color schemes. This includes, custom classes to store the Shadcn color tokens, FlexSchemeColor implementations of them and FlexScheme enums of the configs to make it easy to use them.

    The FlexScheme enums for using the Shadcn colors are:

    • FlexScheme.shadBlue
    • FlexScheme.shadGray
    • FlexScheme.shadGreen
    • FlexScheme.shadNeutral
    • FlexScheme.shadOrange
    • FlexScheme.shadRed
    • FlexScheme.shadRose
    • FlexScheme.shadSlate
    • FlexScheme.shadStone
    • FlexScheme.shadViolet
    • FlexScheme.shadYellow
    • FlexScheme.shadZinc

  • The Shadcn color schemes are still considered beta. The current version does not yet support or use the Shadcn default colors for background, surface and container colors. In this release those colors are using FlexColorScheme's monochrome surface colors. Later versions may change this and use the Shadcn surface colors by default when selecting these themes, with an option to switch to FlexColorScheme's monochrome surface colors, which this version currently uses as the only choice.

  • The Shadcn color selections only set default colors, you will have to theme Material to look more like Shadcn yourself by selecting the correct Material components and modifying their properties to look and behave more like Shadcn style. The Themes Playground includes a pre-configured very preliminary configuration that you can use to do this.

  • The Shadcn color features are in this beta release excluded from FlexColorScheme's otherwise rigorous tests.

Themes Playground

FIX

• Playground: Fix code gen for the first scheme, see [issue #275](rydmike/flex_color_scheme#275).

... (truncated)

• cf04dd0 Merge pull request #281 from rydmike/version-8-2-0
• 70ddf51 Release: Version 8.2.0
• 2c7e71d FIX: Doc comments, do not use brackets in them when not using refs.
• 65ff1c1 Update changelog with PUB status check info
• e2be6bb ADD: V8-1 hisotry version links and prep for V8.2.0 release
• 74e2f11 Change log: Remove TODOs pushed to 8.3.0 or later and set version t 8.2.0-dev.1
• c2a2050 Playground: Add BETA version of a Shadcn UI Premade Design config
• 2e075de Remove usage of in beta 3.31 deprecated ThemeData.indicatorColor and update t...
• e6ed9aa Shadcn as beta: Document Shadcn features as beta and exclude from tests.
• 189eda1 Migrate: Some int alpha based opacity values over to double based opacity values
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)